home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19941221-19950208
/
000062_news@columbia.edu_Sun Jan 1 07:04:59 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
4KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA18395
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Sun, 1 Jan 1995 15:25:00 -0500
Received: by apakabar.cc.columbia.edu id AA13451
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sun, 1 Jan 1995 15:24:59 -0500
Path: news.columbia.edu!panix!news.mathworks.com!news2.near.net!howland.reston.ans.net!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit & the strange DOS machine
Message-Id: <1995Jan1.130459.36285@cc.usu.edu>
Date: 1 Jan 95 13:04:59 MDT
References: <wpfulmorD1pIp4.Aon@netcom.com>
Organization: Utah State University
Lines: 65
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <wpfulmorD1pIp4.Aon@netcom.com>, wpfulmor@netcom.com (william p fulmor) writes:
> I have a single board 8 mhz 8088 MSDOS computer which is an expansion
> board to a unix based computer. COM1 is irrevocably tied to a
> non-standard on-board-modem. COM2 is said to be a standard PC serial
> port, which *was* driven by an NS 8250. COM2 is *now* driven by an NS
> 16550. \|^)
>
> After starting Kermit (3.13 patch 20) in the usual fashion, if I 'set port 2'
> Kermit finds and acknowleges the existance of the 16550 in response to
> either 'sho comm' or 'sho mod'. If I start Kermit with 'set port 2' in
> the command line, it does *not* acknowlege the existance of the 16550. I
> don't know if Kermit finds the 16550 under that circumstance (I have
> commented out 'set port 1' in mscustom.ini).
>
> If I 'dial nnnnnnn', Kermit initializes the modem (Dataport 14400) at
> 57600, dials the number and connects at 14400. With very little tuning, I
> transferred a text file at 2600~2700cps apparently error free from the
> remote Kermit 5A(189) putting out allegedly at 38400.
>
> So why am I using this bandwidth?
I don't quite understand this last question. Your telco line is
limited to 14,400 bps plus whatever compression can do (in Kermit, in the
modem). 2600 cps is about 26,000 bps equivalent and that implies a
compression of 2:1 (rather better than average).
> 1. Kermit takes 13 minutes from pressing <return> following the dial
> command to actually dialing the number. It frequently takes so long to
> return to the prompt after connection is made that the connection drops
> before I can get the remote's attention. "output atdtnnnnnnn\13' is a
> crude work-around.
That's a sure sign of hardware troubles (interrupts are lost,
horribly for example).
> 2. Escaping from connect to local is prompt, but connecting back to
> remote takes a *long* time.
Ditto.
> 3. In interactive operation as a vt100 and with 'set flo rts/cts' a
> very few characters are dropped, not enough to cause problems - but - The
> screen is written only a few lines at a time with long pauses in
> between. I suspect the remote gets bored with the constant hardware halts &
> looses interest. If I 'set flo none' the screen is uninteligible.
Flow control is the likely suspect and the other end thinks
you have stopped the flow. Again, serious hardware problems can mess up
serial port handshaking.
> I suspect that this behavior is caused by Kermit's finding the
> non-standard modem at COM1 and using BIOS thereafter. Can anyone verify
> my suspicions? Is there a way to fool Kermit or to cause it to find COM2
> only? Do any other non-standard hardware features cause Kermit to slow
> down in this fashion?
Kermit will tell your about BIOSn. Just use SHOW COM to see it.
SET PORT COM2 tells Kermit to use that port, and be sure there are no
port-sensing commands before it (SHOW COM is a sensing command) so that
the default COM1 is not touched by them. Try placing SET PORT COM2 near
the top of file mskermit.ini to ensure that's the default port when the
scripts run.
"Non-standard hardware features" covers rather much territory and I
hesitate to begin speculating what your computer really looks like at the
hardware level.
Joe D.